Aprimo API
★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey3 EndpointsREST
For Agents
Authenticate against an Aprimo tenant and retrieve digital asset records and metadata for use in marketing workflows.
Use for: I need to fetch a digital asset record from Aprimo, Get the metadata for an Aprimo resource by ID, List all resources available in our Aprimo tenant, Retrieve an Aprimo access token for the next API call
Not supported: Does not handle creative production, campaign planning, or asset transformation - use for retrieving Aprimo digital asset records only.
Jentic publishes the only available OpenAPI specification for Aprimo API, keeping it validated and agent-ready. Aprimo is a digital asset management and marketing operations platform used by enterprise marketing teams to store, organise, and distribute brand assets. The API exposes token-based authentication and resource retrieval so agents can fetch metadata and asset records from an Aprimo tenant. The current spec covers core access patterns: obtaining an access token, listing resources, and fetching individual resource details by ID.
Install Jentic One Beta
Connect the Aprimo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aprimo 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%2Faprimo.com%2Faprimo" | 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%2Faprimo.com%2Faprimo" | 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 Aprimo API.
Exchange an API key for a short-lived bearer token via the auth endpoint
List digital asset resources stored in an Aprimo tenant
Fetch a specific asset resource by its identifier with full metadata
Pipe Aprimo asset metadata into downstream marketing automation steps
Confirm an asset exists before referencing it in a campaign brief
Use Cases
Patterns agents use Aprimo API for, with concrete tasks.
★ Brand Asset Lookup for Campaign Briefs
Fetch approved digital asset records from an Aprimo tenant to populate campaign briefs with the correct logos, images, and product shots. Marketing operations teams use this to avoid stale or off-brand assets being copied between tools. The API returns asset metadata that can be used to construct downstream URLs, captions, and rights-cleared references.
Authenticate with an API key, list resources in the Aprimo tenant, then fetch the resource matching a given asset ID and return its metadata.
Asset Inventory Audits
Periodically list resources in an Aprimo tenant to track how many approved assets exist for each brand or product line. Marketing operations teams use this to surface gaps in coverage and to feed reporting dashboards. The list endpoint provides the source data that downstream analytics or BI tools transform into inventory views.
Call the list resources endpoint, paginate through all results, and produce a count of assets grouped by metadata field.
AI Agent Asset Retrieval via Jentic
An AI agent that drafts marketing copy or social posts can use Jentic to call Aprimo and fetch the correct, brand-approved asset for a given product. This avoids the agent inventing image URLs or referencing unapproved files. Through Jentic, the agent issues a search query, loads the Aprimo schema, and executes a resource fetch with the asset ID supplied by the user.
Use Jentic search 'fetch a digital asset from Aprimo', load the Aprimo schema, then call the resource fetch with a specific asset ID and return the metadata to the calling agent.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for aprimo api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Exchange API key for an access token
GET
/resources
List digital asset resources
GET
/resources/{id}
Fetch a single resource by ID
POST
/auth/token
Exchange API key for an access token
GET
/resources
List digital asset resources
GET
/resources/{id}
Fetch a single resource by ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Aprimo by hand means calling its /auth/token endpoint to exchange your API key for an access token and then paging its resource endpoints yourself. Through Jentic you install once, import the Aprimo API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Aprimo puts the resource id in the URL path (/resources/{id}) and the asset operations here are read-only, so a rule can pin your agent to reading specific digital asset records. You choose the operations it may call, so the agent only reads the resources you have added.
Credential isolation
Your Aprimo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'fetch a digital asset from Aprimo', and Jentic returns the matching Aprimo operation with its input schema so the agent calls the right endpoint without browsing docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Aprimo API through Jentic.
Why is there no official OpenAPI spec for Aprimo API?
Aprimo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Aprimo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Aprimo API use?
The Aprimo API uses an API key, exchanged via POST /auth/token for a bearer access token that is then sent on subsequent requests. Through Jentic, the API key is stored encrypted in the vault and never enters the agent's context - the agent receives a scoped token only.
Can I list every digital asset in my Aprimo tenant with this API?
Yes. Call GET /resources to list digital asset resources in your tenant. The list endpoint returns asset records with metadata; use GET /resources/{id} to fetch full details for a specific asset.
What are the rate limits for the Aprimo API?
The OpenAPI spec does not define explicit rate limits. Aprimo enforces tenant-level throttling that varies by plan; check your Aprimo administrator console for the limits applied to your tenant.
How do I fetch an Aprimo asset through Jentic?
Install Jentic with pip install jentic, search for 'fetch a digital asset from Aprimo', load the schema for GET /resources/{id}, then execute with your asset ID. Jentic resolves authentication for you against the stored API key.
Is the Aprimo API free?
No. Aprimo is an enterprise SaaS platform; API access is included with an Aprimo tenant subscription. Pricing is negotiated directly with Aprimo and depends on tier and seat count.
Can I limit what my agent is allowed to do with the Aprimo API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use with Aprimo. The Aprimo operations here are read-only and address each asset by its id in the path (GET /resources/{id}), so you can pin the agent to listing resources or reading only the specific digital asset records you have added. The agent calls just the operations you allow, and nothing else.
GET STARTED