ERP.AI
Build on the business foundation.
Use supported APIs to connect your application, agent, or integration to the records and capabilities it needs.
Start with the platform and the specific app.
The platform reference describes supported resource areas and authentication. Each application’s For your agent guide explains its business model and links to the relevant references. Use both: one establishes the connection, the other provides the domain context.
Sign in to the intended environment and organization. Discover the app available to your account and use its actual identifier for authenticated work. Public application names and catalogue routes are useful discovery aids, but they do not identify your organization’s installed app.
Choose the smallest useful operation.
Read and inspect
Start with the app and schema, then read a narrow set of records needed to verify the mapping and access.
Create a controlled change
Use a non-sensitive test case and confirm the returned result in the application.
Handle errors
Distinguish authentication, access, validation, and transient failures. Keep useful diagnostics without storing secrets.
Scale responsibly
Use documented server-side filters, counts, aggregates, and bulk operations where appropriate instead of fetching every record.
Treat client code as part of the operating system.
Maintain an integration owner, environment configuration, credential rotation process, and monitoring route. Review permissions when the client’s task changes, and test behavior after relevant schema or workflow releases.
The pricing page is the current source for API-key operations, workflow execution, AI, and retained-capacity rates. Include these meters when estimating the cost of an automated process.
Put ERP.AI to work for your business.
Choose an application, then configure the records, roles and workflows your team needs.