Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey3 EndpointsREST
For Agents
Exchange credentials for an access token, list Domo resources, and fetch a specific resource by ID using an Authorization header API key.
Use for: Get an access token for the Domo API, List all resources in my Domo instance, Fetch a Domo resource by its ID, Check whether a specific Domo resource exists
Not supported: Does not handle dataset row-level CRUD, dashboard rendering, or user provisioning - use for token exchange and resource metadata listing only.
The Domo API exposes the cloud business intelligence platform's resource model through a REST interface. The curated specification covers three core operations: token exchange via POST /auth/token, listing available resources, and fetching a single resource by ID. Authentication uses an Authorization header API key. The API supports analytics workflows that read dataset, dashboard, or other resource metadata for downstream automation or governance reporting, and is intended as an entry point to the broader Domo developer surface.
Install Jentic One Beta
Connect the Domo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Domo API, 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%2Fdomo.com%2Fdomo" | 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%2Fdomo.com%2Fdomo" | 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 Domo API.
Obtain an access token via POST /auth/token
List available Domo resources with GET /resources
Fetch a single resource by ID via GET /resources/{id}
Authenticate every call with an Authorization header API key
Inspect resource metadata to drive downstream analytics jobs
Use Cases
Patterns agents use Domo API for, with concrete tasks.
★ Resource Inventory and Governance
Build a governance report by calling GET /resources and walking each entry with GET /resources/{id} to capture metadata. This supports audits, dataset cleanup, and access-review jobs that need a current picture of what exists in the Domo instance without querying the underlying datasets.
POST /auth/token to get an access token, GET /resources, then GET /resources/{id} for each entry and write the names and IDs to a CSV.
Token Lifecycle Management
Automate token refresh by calling POST /auth/token whenever the current access token nears expiry. Storing the refreshed token in a secrets manager keeps long-running BI automations alive without manual intervention from the Domo administrator.
Schedule a job that calls POST /auth/token every 50 minutes and updates the stored token in the secret manager.
AI Agent Analytics Lookup via Jentic
An AI agent uses Jentic to look up Domo resources on demand: it searches for an analytics intent, loads GET /resources, executes it, and pipes the IDs back to a user or another tool. The Domo API key stays in your Jentic One instance, so the agent never holds the credential while iterating over the resource list.
Search Jentic for 'list domo resources', execute GET /resources, and return the first 10 results to the user with their IDs.
Key Endpoints
3 endpoints — the domo api exposes the cloud business intelligence platform's resource model through a rest interface.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Exchange credentials for an access token
GET
/resources
List available resources
GET
/resources/{id}
Get a single resource by ID
POST
/auth/token
Exchange credentials for an access token
GET
/resources
List available resources
GET
/resources/{id}
Get a single resource by ID
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.
D
Domo API
- Foundational (C+)60/100
93
Foundational Compliance58
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability50
Security50
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
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.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
33%
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.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
27%
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.
50%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
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 the Domo API by hand means minting a token through /auth/token, carrying it on the Authorization header, and refreshing it before resource-metadata calls succeed. Through Jentic you install once, import the Domo API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Domo puts the resource id in the URL path (/resources/{id}), so a rule can pin your agent to one resource for metadata reads. You choose the operations it may call, so it can exchange a token and list or read the resources you allow and nothing more.
Credential isolation
Your Domo API key and minted tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time on the Authorization header. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list domo resources' or 'get a domo access token', and Jentic returns the matching operation with its parameter schema so the agent calls the right endpoint without consulting the spec.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Domo API through Jentic.
What authentication does the Domo API use?
The spec defines an Authorization header API key (ApiKeyAuth). Tokens are minted by POST /auth/token and passed in subsequent requests. Through Jentic, both the static key and minted tokens are stored encrypted in the vault and injected at execution time.
Can I list resources with the Domo API?
Yes. GET /resources returns the available resources for the authenticated client, and GET /resources/{id} fetches details for a specific resource by ID.
What are the rate limits for the Domo API?
The OpenAPI spec does not declare explicit rate limits. Domo's broader developer documentation specifies per-endpoint limits, so apply exponential backoff on 429 responses and avoid burst patterns when iterating GET /resources.
How do I get an access token through the Domo API via Jentic?
Run pip install jentic and search for 'get a domo access token'. Jentic returns POST /auth/token; execute it with the stored client credentials and Jentic stores the resulting token for downstream calls so the agent never handles the secret.
Can I fetch a specific Domo resource?
Yes. GET /resources/{id} returns the metadata for the resource with the given ID. Use GET /resources first to discover IDs if you do not already have them.
Is the Domo API free to use?
Access requires a Domo subscription. The API is included with Domo plans rather than priced per call, but quota and capability depend on the plan. Check your Domo admin console for the limits that apply to your tenant.
Can I limit what my agent is allowed to do with the Domo API?
Yes. Because you run Jentic One yourself, your own rules decide which Domo operations the agent may call, so you can allow it to exchange a token via POST /auth/token and list resources with GET /resources while blocking everything else. Since Domo puts the resource id in the URL path (GET /resources/{id}), a rule can pin the agent to a single resource for metadata reads. Your Domo API key stays in your instance and is injected only for the calls you permit.
GET STARTED