This guide explains the RD Station application programming interface (API). It describes various API operations, related request and response structures, and error codes. The current version of RD Station API is 2.0.

Welcome to RD Station API

Our API is built to allow you to create an integration quickly and easily. The ecosystem of developers creating integrations over our APIs is strong and diverse, from webinar providers to CRMs.

All of our APIs are organized around REST - if you've already interacted with a RESTful API, many of the concepts will be familiar to you. All API calls to RD Station must be made to the base domain https://api.rd.services. We use many standard HTTP features, such as HTTP verbs, which can be understood by many HTTP clients.

A JSON will be returned in all API responses, including errors. APIs are designed to have predictable and direct URLs and use HTTP response codes to indicate API errors.

API Reference

This documentation helps you to implement the RD Station v2 API.
This API uses a JSON format for output.
All API requests are authenticated through an access token sent in the request, which must be obtained following the described steps in the Authentication flow.

API Objects

There are two main objects you will find in the API: Contacts and Custom fields, see the anatomy of these objects, and learn about their properties in the reference section.

Contacts Custom fields