The Current RMS API is a way of connecting to Current RMS systems. It lets developers read and write data, meaning they can get data about existing records as well as create new records and update existing ones. API access requires an active subscription, as it is not available for trial accounts due to security reasons.

As our API has matured, we’ve attracted a flourishing community of developers who use our API to create exciting integrations with other solutions or extract data for company projects.

Some companies have started to make their integrations available for everyone to use, extending the functionality in Current RMS. We call these “third party integrations” because they are not developed or maintained by the Current team.

No third-party integrations are turned on in your system by default. You’re in control of the API, so you can choose which software and services to connect with. If your account is currently on a trial, you will need to upgrade to a paid account to enable and utilize API resources.

Our integrations

We wrote all of the code to make these integrations work and we are responsible for keeping them up to date. If something isn’t working correctly, we’ll investigate and fix it where we can. We also provide support guides and are happy to help you set up these integrations. For detailed developer resources, you can refer to our API Documentation and utilise our Postman Collection to streamline your API integration process.

Third-party integrations

If you find any other integrations with Current, they were not developed by the Current RMS team.

While we love hearing about what people have done with our API and many third-party integrations work well, keep in mind that absolutely anybody can use our open API to create an integration.

We can’t make any assurances or guarantees about the third-party vendor that provides the integration.
Our own features go through multiple levels of human and machine testing. We do not test or verify third-party integrations in the same way.
The third-party vendor is responsible for maintaining the integration. If it’s not working as expected, it’s their responsibility to fix it.

it's for these reasons our Support team can’t provide support on how to set up or use third party integrations.

Data security

To use an integration, you’ll usually need to provide authorisation or share an API key. When you authorise or provide an API key, you’re providing full read and write access to your Current RMS system. This process involves making secure API calls authenticated through API keys or OAuth2 mechanisms, ensuring the safety and integrity of your data.

An example of an authorisation prompt

Think very carefully before providing authorisation or sharing your keys. In the same way that you’d keep your password safe, only authorise or share your keys with software or services that you trust.

Remember that you can remove or refresh keys in System Setup > Integrations > API and manage OAuth2 authorised applications under the “Connected Apps” heading.

Data privacy

Third party integrations are beyond the scope of our privacy policy. Often, they may take data from your Current RMS system and use or store it in other applications or services.

It’s your responsibility to check the privacy practices of third-party vendors to make sure that you’re handling data legally and safely at your business.

Using the Current RMS API

Accessing Completed Opportunities

The Current RMS API allows the retrieval of various types of data, including completed opportunities. Developers can consult resources such as the API Documentation and the Postman Collection for endpoint specifics.

Adding Items to Opportunities

Using the API, items can be programmatically added to opportunities, which enables more dynamic workflows. While customization support isn't provided, developers can refer to documentation for detailed instructions. For technical issues, such as bugs or missing features, support is available from Current RMS.

What are third party integrations?