Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Analyze Todoist Data in Infragistics Reveal
Use the CData API Server to create an OData API on top of Todoist data and visualize live Todoist data in Ingragistics Reveal.
Reveal is a data visualization solution provided by Infragistics and can be paired with the CData API Server and Todoist ADO.NET Provider to build dynamic dashboards from live Todoist data. The CData API Server generates an OData API for Todoist, which is natively consumable in Reveal. In this article, we walk through connecting to Todoist in API Server and connecting to the API Server from Infragistics Reveal to create a simple dashboard.
Connect to Todoist from API Server
CData API Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.
- Open API Server and click Settings -> Connection -> Add Connection
- Select "Todoist"
- Enter the necessary authentication properties to connect to Todoist.
Start by setting the Profile connection property to the location of the Todoist Profile on disk (e.g. C:\profiles\Todoist.apip). Next, set the ProfileSettings connection property to the connection string for Todoist (see below).
Todoist API Profile Settings
To authenticate to Todoist, and connect to your own data or to allow other users to connect to their data, you can use the OAuth standard.
First, register an OAuth application with Todoist. To do so, go to App Management Console, create a new application and configure a valid OAuth redirect URL. Your Oauth application will be assigned a client id and a client secret.
After setting the following connection properties, you are ready to connect:
- AuthScheme: Set this to OAuth.
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
- OAuthClientId: Set this to the client_id that is specified in you app settings.
- OAuthClientSecret: Set this to the client_secret that is specified in you app settings.
- CallbackURL: Set this to the Redirect URI that is specified in your app settings
Add Todoist Resource Definitions in API Server
After connecting to Todoist, create Resources, which represent API endpoints for Todoist data.
- Click Settings -> Resources -> Add Resource
- Select the Todoist connection
- Select the table you wish to retrieve and click Next
- (Optional) Edit the resource to select specific fields and more
- Save the settings
Add an API Server User
Create a User to connect to Todoist from Reveal through API Server.
- Click Settings -> Users
- Click Add
- Configure a User with access to the Todoist Connection and Resource(s)

(Optional) Configure Cross-Origin Resource Sharing (CORS)
When accessing and connecting to multiple different domains from an application such as Ajax, there is a possibility of violating the limitations of cross-site scripting. In that case, configure the CORS settings in Settings -> Server.
- Enable cross-origin resource sharing (CORS): ON
- Allow all domains without '*': ON
- Access-Control-Allow-Methods: GET, PUT, POST, OPTIONS
- Access-Control-Allow-Headers: Authorization
Save the changes to the settings.

Create a Dashboard in Reveal
With the API Server configured, we can visualize Todoist data in Reveal.
- Log into Reveal and click Dashboards -> New
- Click Data Source -> OData Feed
- Specify the API Server API endpoint URL, for example: https://serverurl/api.rsc
- Select Generic Credentials and specify the API Server username and authentication token
- Select the entity you wish to visualize
- Select fields and choose a chart type
More Information & Free Trial
At this point, you have created a simple dashboard from live Todoist data. For more information on creating OData feeds from Todoist (and more than 150 other sources), visit the API Server page. Download a free, 30-day trial and start working live Todoist data in tools that consume OData APIs.