The Veracity Services API provides information about the currently logged in user (my) and your application in general (this). To call these APIs you need to have an access token for the current user as well as a subscription key. The former can be retrieved once a user authenticates with your application while the latter can be found in the Veracity for Developers resource portal. Head over to https://developer.veracity.com/projects and create an Application resource there to create a subscription key for your application. You can read more about how to authenticate users from your application in the Identity documentation.

Grouping

The API is grouped into 3 distinct sections, each with their own intent.

My: Return information about the currently logged in used as defined by their access token.
This: Return information about your application.
Options: These endpoints are for maintenance purposes. Do not use.

As the API requires the use of an access token unique to a user many of the endpoints will include information specific to that user. E.g.: the /my/profile endpoint will return profile information for that user without any additional query parameters as the users is identified by their access token.

Multiple root urls

The API is versioned in order to provide a consistent contract for your application to call. You can decide yourself if you want to use one or the other. The APIs describe on this page will always be the latest version.

https://api.veracity.com/veracity/services/v3

Veracity commits to actively support the latest version of the API as well as the next previous version. This currently means v3 and v2 of the Veracity Services API.