serviceSelect the service
Choose the service that owns the operation you want to perform.
Work across services with a common request structure. Choose the action, pass the inputs, and request the data your experience needs.
Requests use a POST to /services/ with a JSON body. The service and action select the operation; parameters and options describe the request.
This editable template illustrates the request structure. Use the API reference and your environment’s credentials for an actual integration.
Open the API referenceReplace placeholders with documented service and action names.
serviceChoose the service that owns the operation you want to perform.
actionUse the documented action name for the capability you need.
paramsSupply the positional parameters required by that action.
optionsApply supported filters, limits, ordering, or related-data flags.
schemaRequest the fields and supported relationships your interface needs.
eventsExplore ArcSignal pub/sub when other parts of your system need to react.
Identify the users, records, assets, and business actions involved. Choose the smallest useful integration.
Request access, review the endpoint contracts, and test the data shape your application needs.
Handle authentication, permissions, failures, and event behavior in the context of your application.
Use MCP-compatible integrations to expose supported Arc capabilities to agents. Design the tool set around the task, supply the relevant context, and keep sensitive actions behind appropriate permissions and review.
From the first user to the whole business workflow.
Let’s build it with Arc Fusion.