<aside> ℹ️
The FAQ here are intended for CARO users and people who have already had some exposure to CARO. If you have just discovered CARO, you might find the introductory resources on our website helpful to get started.
</aside>
You can use the same Client ID and Client Secret to communicate with CARO when acting on behalf of each of your VRS customers.
Bearer tokens have a validity of 24 h. In the absence of any further agreement with us, each client is limited to 150 tokens per 24 hour window. Please reuse each token until its expiry.
<aside> ℹ️
If the use of one client Secret:ID pair or one authentication token for all your VRS customers conflicts with your own architecture, do let us know, since we have no insights into your systems. In that case, we may need to reconsider certain design decisions at our end.
</aside>
The Client ID and Client Secret can be found under Developer Tools.
Only users set up as Service Provider Developers are permitted to see this information. Ask a team member with that access permission to upgrade your role in Team Management.
Be sure to use the correct URLs. The best place to check the required URLs for API calls is the Developer Tools.
One detail of particular importance is the slash in the Audience parameter.
If your API calls still fail, please contact our service team.
Our search returns fuzzy results. So, if you look for a specific corrUUID or DID, make sure to check the returned result, as the search may have found something that is highly similar if there is no exact match.
To enhance your customers’ VRS messages with CARO’s ATP credentials, there are 2 levels of connection you need to implement.