Rd Services API de verticalização
69
AI ReadinessAI-Aware (B+)69/100
Community OpenAPI document · agent-readyCRMContact Managementbearer13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Define RD Station custom objects, create and update records of them tied to a contact, and link records to contacts or other objects through relationships.
Use for: I need to add a property record to the buildings custom object in RD Station, List all custom objects defined in this RD Station account, Find all records linked to the contact maria.silva@rdstation.com, Update the price attribute on an existing custom object record
Not supported: Does not send email campaigns, score leads, or manage deals and pipelines. Use for defining RD Station custom objects and storing related records only.
The API de verticalização extends RD Station with custom objects: you define your own object types, such as properties or vehicles, and store records of them linked to RD Station contacts. Each custom object carries an external_id, a slug, and a label, and each record carries its own external_id, free-form attribute values, and contact metadata such as name and email. Records can be related to other objects, for example to a contact by email, and those relationships are listed, created, and removed through their own operations.
Install Jentic One Beta
Connect the API de verticalização to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API de verticalização, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frd.services%2Frd" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frd.services%2Frd" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API de verticalização API.
Define a custom object type with an external_id, a slug that cannot change after creation, and a label
Search custom object definitions by slug, label, or description with filter parameters and page through results
Create a record under one custom object with its external_id, attribute values, and the contact it belongs to
Update a record's attribute values with PATCH, passing the contact metadata the operation requires
Link a record to another object, such as a contact identified by related_object_id and related_record_id
Find every record related to a given record or object with the filter[related_record_id] and filter[related_object_id] parameters
Exchange a client_id and client_secret for an access token with the client credentials grant
Use Cases
Patterns agents use API de verticalização API for, with concrete tasks.
★ Keeping RD Station records in sync from an AI agent through Jentic
An agent that watches another system, such as a property listing tool, can mirror each new item into RD Station as a custom object record tied to the interested contact. Through Jentic the agent searches for 'create a custom object record', receives the record-creation operation with its data and metadata inputs, and calls it while your self-hosted Jentic One instance handles the client credentials token exchange and injects the bearer token.
POST /v1/custom_objects/{custom_object_id}/records with data.external_id '123556', an attribute value for the listing, and metadata.contact with name 'Maria Silva' and email 'maria.silva@rdstation.com'
Modelling a vertical business inside RD Station
Real estate, automotive, and education businesses track things that are not contacts or deals: buildings, cars, courses. The custom objects operations let you create an object type with a slug like buildings and a label like Imóvel, list existing definitions with slug, label, and description filters, and read one definition by id before adding records.
POST /v1/custom_objects with data.external_id 'sistema_imoveis', data.slug 'buildings', and data.label 'Imóvel', then GET /v1/custom_objects/{id} to confirm the definition
Relating records to contacts
A record becomes useful in marketing once it is linked to the people who care about it. The relationships operations take a related_object_id such as rdsm_contact and a related_record_id such as the contact's email, and the records listing can then be filtered by filter[related_record_id] to find everything tied to one contact.
POST /v1/records/{record_id}/relationships with data.related_object_id 'rdsm_contact' and data.related_record_id 'joao@email.com', then GET /v1/records with filter[related_record_id] 'joao@email.com'
Key Endpoints
13 endpoints — the api de verticalização extends rd station with custom objects: you define your own object types, such as properties or vehicles, and store records of them linked to rd station contacts.
METHOD
PATH
DESCRIPTION
POST
/oauth2/token
Get an access token
GET
/v1/custom_objects
List custom objects
POST
/v1/custom_objects
Create a custom object
POST
/v1/custom_objects/{custom_object_id}/records
Create a record
PATCH
/v1/custom_objects/{custom_object_id}/records/{id}
Update a record
GET
/v1/records
List records by related record or object
POST
/v1/records/{record_id}/relationships
Create a relationship
POST
/oauth2/token
Get an access token
GET
/v1/custom_objects
List custom objects
POST
/v1/custom_objects
Create a custom object
POST
/v1/custom_objects/{custom_object_id}/records
Create a record
PATCH
/v1/custom_objects/{custom_object_id}/records/{id}
Update a record
GET
/v1/records
List records by related record or object
POST
/v1/records/{record_id}/relationships
Create a relationship
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
API de verticalização
- AI-Aware (B+)69/100
64
Foundational Compliance75
Developer Experience & Jentic Compatibility60
AI-Readiness & Agent Experience94
Agent Usability60
Security64
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
64
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
82%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
75
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
54%
Example Density
How richly the API is illustrated with examples.
97%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
60
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: B-Signals: 4
53%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
88%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
64
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
64%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring this API by hand means running the client credentials exchange at POST /oauth2/token, refreshing the bearer token when it expires, and building the nested data and metadata bodies. Through Jentic you install once, import the API de verticalização from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
The custom object id sits in the URL path (/v1/custom_objects/{custom_object_id}/records), so a rule can pin your agent to one custom object's records. You choose the operations it may call, so destructive ones like record deletion or relationship removal are not included unless you add them.
Credential isolation
Your client_id and client_secret are stored once, encrypted, by your own Jentic One instance and the resulting token is injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a custom object record' or 'link a record to a contact', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the Portuguese reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using API de verticalização API through Jentic.
What authentication does the API de verticalização use?
Per its OpenAPI spec, the API uses bearer tokens in the Authorization header. You get the token from POST /oauth2/token with the client credentials grant, sending grant_type, client_id, and client_secret; that token operation itself is open. Through Jentic, the client_id and client_secret are stored encrypted by your own Jentic One instance and the token is injected at execution time, so neither enters the agent's context.
Is there an RD Station custom objects MCP server?
You don't need an MCP server to give your agent the API de verticalização. Jentic connects it directly from the API Directory: import it, store your client credentials once, and your agent calls it. Operations are discovered on demand, so the agent's context holds only the operation it is about to call.
Can I limit what my agent is allowed to do with the API de verticalização?
Yes. For example, allow only GET and POST on /v1/custom_objects/123/records for one custom object, so the agent can read and add records of that type but cannot delete records, remove relationships, or define new object types. Every call it makes is logged.
What fields does a new record need?
POST /v1/custom_objects/{custom_object_id}/records requires both data and metadata. Inside data, external_id is required and the remaining keys are your object's attribute values as text, numbers, or date-times; metadata needs a contact object. Optional relationships can be created in the same call.
Can I change a custom object's slug after creating it?
No. The spec describes slug as the readable identifier used to reference the object in the API and states it cannot be changed after creation, so choose it carefully when calling POST /v1/custom_objects.
What are the rate limits for the API de verticalização?
The OpenAPI spec does not specify rate limits. Check https://developers.rdstation.com for current limits before bulk-loading records.
How do I add a custom object record through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the API de verticalização from the API Directory, and store your client_id and client_secret. Your agent searches for 'create a custom object record', receives the record-creation operation with its input schema, and calls it with the record and contact. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED