- System
- Accounts
- Addresses
- Assets
- Budgets
- Contacts
- Contracts
- Countries
- Currencies
- Customers
- Employees
- Invoices
- Locations
- Meters
- Organizations
- Partners
- Quotes
- Receipts
- Units
- Vendors
- Query
- Passthrough
- Raw
- OAuth
- MCP
- List the platforms an MCP user can see and use
- Resolve whether an MCP user may execute tools against a platform
- The folded tool policy of this MCP user on a platform
- Ask an administrator for a tool this MCP user is denied
- List the tool catalogue of a platform for this user
- Execute one MCP tool against a platform for this user
- Writes
- Work Orders
- Update a work order’s status (legacy alias of the set-status action)
- Fetch the record of a queued write (legacy alias of GET /v4/writes/{writeId})
- List work orders
- Create a work order
- Get a work order
- Update a work order
- Delete a work order
- Assign a work order
- Accept a work order
- Reject a work order
- Start a work order
- Hold a work order
- Resume a work order
- Complete a work order
- Close a work order
- Cancel a work order
- Set the status of a work order
- Convert a work order
- Taxonomies
- Business Units
- Users
- Labor Resources
- Asset Assignments
- Meter Readings
- Alarms
- Dispense Transactions
- Work Requests
- Work Tasks
- Maintenance Templates
- Maintenance Triggers
- Events
- Event Recurrences
- Order Materials
- Order Resources
- Comments
- Inventory Items
- Stock Levels
- Supply Options
- Purchase Orders
- Purchase Order Lines
- Invoice Lines
- Budget Lines
- Work Centers
- Production Routings
- Production Routing Operations
- Bills Of Material
- Bill Of Material Lines
- Production Orders
- Production Order Operations
- Purchase Requisitions
- Purchase Requisition Lines
- Quote Lines
- Sales Orders
- Sales Order Lines
- Return Orders
- Return Order Lines
- Shipments
- Shipment Lines
- Receipt Lines
- Inventory Transactions
- Leases
- Lease Applications
- Projects
- Inventory Documents
- Checklists
- Checklist Items
- Attachments
- Management API
- Connections
- List connections
- Create a connection (real with credentials, or intended)
- Get one connection
- Update a connection
- Soft-delete a connection
- Permanently delete a connection
- Activate or deactivate a connection (inactive is refused by /v4, MCP and sync, but is not a deletion)
- The forms, solutions and flow folders of a connection, and which are on
- Set exactly which forms, solutions and flow folders are on for a connection
- Issue a connection-scoped access token for one of your connections
- Embed
- Mint a short-lived embed session for a connection’s settings form
- Read the settings an end user saved for a connection
- Store an end user’s submitted settings (first-party only)
- Flip the end user’s kill switch for a connection’s settings form (first-party only)
- Disconnect a connection from inside the embed (first-party only)
- Read the form a custom-modal field's endpoint defines (first-party only)
- One page of a connection’s support requests (first-party only)
- Open a support request for a connection (first-party only)
- One support request and its public thread (first-party only)
- Reply to a support request (first-party only)
- One file from a support request (first-party only)
- Open one of your customers’ embedded experience: their connections, connecting another, each connection’s forms
- Resolve an embed session token into everything the embed renders (first-party only)
- List the client’s embed settings forms
- Read one of the client’s embed settings forms
- Create or replace one of the client’s embed settings forms
- Delete one of the client’s embed settings forms, with every connection’s answers to it
- Clients
- Secrets
- Redirect URIs
- Whitelabel
- Log Retention
- Webhook Endpoints
- Support
- One page of an application’s support requests, from its team and its end users
- Open a support request for an application, as a named member
- One of an application’s support requests and its public thread
- Reply to an application’s support request, as a named member
- One file from an application’s support request
- Store one file for a later support request or reply
- Platforms
- Compat
- v1 compatibility: GET /api/system/platforms (temporary, removed at the end of November 2026)
- v1 compatibility: GET /api/system/connections (temporary, removed at the end of November 2026)
- v1 compatibility: POST /api/system/connections (temporary, removed at the end of November 2026)
- v1 compatibility: POST /v1/embed/session (temporary, removed at the end of November 2026)
- Field Mappings
- Read a connection’s field mappings: what it serves and the active mapping document
- Save a connection’s field mappings as a new revision
- List a connection’s field-mapping revisions, newest first
- Activate an earlier field-mapping revision
- Replace a connection’s custom streams
- Test-fetch a (possibly unsaved) custom stream against the live vendor endpoint
- Read the source tables and columns a connection’s mappings can use
- Data Mappings
- List the entities of a connection that are mapped to the customer’s own identifiers
- Start mapping one entity of a connection
- Read one data mapping’s definition
- Change a data mapping’s cardinality
- Stop mapping an entity, discarding its pairs
- Read one page of a data mapping’s pairs
- Replace a data mapping’s pairs wholesale
- MCP
- Create an MCP role (first-party only)
- List a client’s MCP roles (first-party only)
- Update an MCP role (first-party only)
- Delete an MCP role, optionally reassigning its users (first-party only)
- List end customers
- Register an end customer
- Which metadata key names a connection’s end customer
- Set the metadata key that names a connection’s end customer
- One customer, with its counts
- Rename a customer, or re-point the provider’s identifier for them
- Remove one of the provider’s customers
- List one customer’s MCP users
- Provision an MCP user for one of the provider’s customers
- Update one of a customer’s MCP users
- Offboard one of a customer’s MCP users
- Read one of a customer’s MCP users
- Mint a personal access token for one of a customer’s MCP users
- List the personal access tokens of one of a customer’s MCP users
- End one personal access token of one of a customer’s MCP users
- Connect a platform for one of a customer’s agents
- List one customer’s connections
- List one customer’s MCP roles
- Create a role for one customer
- Rename a customer’s role, or make it their default
- Delete a customer’s role, optionally reassigning its users
- Read one of a customer’s MCP roles
- What one customer sees, and what it inherits
- Which platforms a customer has company-wide credentials for
- What to send for a customer’s company-wide credentials, and what is stored
- Set one customer’s company-wide credentials for a platform
- Stop supplying a customer’s company-wide credentials for a platform
- What one customer has set up: every platform on for it, its sign-in choice, and what it stored
- The customer’s live setup link, if any — who it went to and when it dies, never the code
- Mint the customer’s setup link, replacing a live one
- Revoke the customer’s live setup link
- Record whom the live setup link was emailed to
- The customer’s choice for one platform: one shared account for everyone, or each person from their agent
- Remove the customer’s sign-in to one platform: its shared account, its API key or its company-wide fields
- What one of a customer’s roles may call on a platform
- Set a page of tool permissions for one of a customer’s roles
- Enable or disable every tool on a platform for one of a customer’s roles
- Override, or clear, one platform for one customer
- Create an MCP user (first-party only)
- List a client’s MCP users (first-party only)
- Update an MCP user (first-party only)
- Soft-delete an MCP user (first-party only)
- Give a pending MCP user its seat (first-party only)
- Issue a personal access token for an agent (first-party only)
- List an agent’s personal access tokens (first-party only)
- End one of an agent’s personal access tokens (first-party only)
- Connect a platform for an agent (first-party only)
- Read a client’s platform visibility (first-party only)
- Set the platform-visibility default, and optionally the decided platforms (first-party only)
- Show or hide one platform (first-party only)
- The workspace’s third-party MCP servers: catalog and custom (first-party only)
- Register a custom MCP server by URL (first-party only)
- Edit a custom MCP server (first-party only)
- Remove an MCP server from the workspace (first-party only)
- Start an OAuth sign-in to a third-party MCP server: the workspace's or one person's (first-party only)
- Sign in to the server now and load its tool list (first-party only)
- List an adapter’s tool catalogue, searched and paginated (first-party only)
- One level’s guardrail rules on a platform, every tool (first-party only)
- Replace one tool’s guardrail rules at one level (first-party only)
- Relabel a tool or rewrite its description for this workspace (first-party only)
- List the platforms a client has company-wide credentials for (first-party only)
- Read one platform’s company-wide credential form and state (first-party only)
- Set a platform’s company-wide credentials (first-party only)
- Clear a platform’s company-wide credentials (first-party only)
- Read the tool policy for a page of tool names (first-party only)
- Write the tool policy for a page of tool names (first-party only)
- Flip one level’s tool-policy default, wiping its exceptions (first-party only)
- Access requests of the workspace, newest first (first-party only)
- Grant a pending access request to the person or their role (first-party only)
- Dismiss a pending access request (first-party only)
Replace the value of a redirect URI
PUT
https://api.makini.io/v4/clients/{clientId}/redirect-uris/{uriId}
Request
Path Params
Body Params application/jsonRequired
Examples
Responses
🟢200OK
application/json
Bodyapplication/json
🟠400Bad Request
🟠401Unauthorized
🟠403Forbidden
🟠404Record Not Found
🔴500Server Error
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request PUT 'https://api.makini.io/v4/clients//redirect-uris/' \
--header 'Content-Type: application/json' \
--data '{
"uri": "string"
}'Response Response Example
200 - Example 1
{
"redirectUri": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"uri": "string",
"createdAt": "2019-08-24T14:15:22.123Z",
"updatedAt": "2019-08-24T14:15:22.123Z"
}
}Modified at 2026-10-16 14:17:58