Plur-e
Developers

Developers

Plur-e for developers — connect AI clients over MCP or call the Plur-e public REST API with a tenant API key to read and write Business Central, Dynamics 365 CRM and mobile-panel data.

Quick answer

The Developers section of the Admin Center has two parts: AI & MCP, to connect AI assistants to Business Central and Dynamics 365 CRM, and APIs, a public REST API for your own integrations. The API lives at https://api.plur-e.com/api/public/v1, answers JSON and authenticates with a tenant API key sent as Authorization: Bearer plrapi_…. It needs the Developer APIs module in your subscription; each key carries scopes and the same roles that gate MCP, so it can never do more than you allow.

What you get

PartWhat it isWhere to start
AI & MCPRemote MCP servers for AI assistants, gated by MCP rolesPlur-e MCP servers
APIsPublic REST API for scripts, back-end services and integrationsThis section

The API has three areas, all under the same base URL:

AreaPathWhat it does
Business Central/bcRuns the catalogued Business Central methods and read-only OData queries
Dynamics 365 CRM/crmReads, creates, updates and deletes Dataverse records, and runs actions
Plur-e panel/panelReads mobile users, devices, locations, activity, roles and modules

Requirements

  • The Developer APIs module licensed on your Plur-e subscription. Without it, creating a key answers error 1320 and every API call is refused with the same error. Listing and revoking keys keeps working so you can clean up.
  • A tenant administrator to create keys (the admin role of the tenant). Support staff can see keys but not create or revoke them.
  • For Business Central: the Business Central environment and company configured in Developers → AI & MCP → Settings. The API always uses that environment and company; you cannot pick another one per request.
  • For Dynamics 365 CRM: a connected CRM in Developers → AI & MCP → Dynamics 365 CRM. A key is bound to one CRM connection.

Base URL and format

https://api.plur-e.com/api/public/v1
  • Requests and responses are JSON. Property names are camelCase.
  • Every request needs the Authorization: Bearer <YOUR_API_KEY> header. See Authentication.
  • Errors use application/problem+json. See Errors.
  • The API is versioned in the path (v1). Calls are rate limited per key; see Authentication.

Your first call

List the Business Central methods your key may run:

curl -s "https://api.plur-e.com/api/public/v1/bc/methods" \
  -H "Authorization: Bearer <YOUR_API_KEY>"

A 200 answer is a JSON array. A 401 answer means the key is wrong, revoked or expired; the detail field says which one.

Security in one minute

  • A key is shown once, when you create it. Plur-e stores only a hash of it.
  • Every key has an expiry (30, 90, 180 or 365 days) and can be revoked at any time.
  • Scopes limit the kind of operation (read, write, post, delete); roles limit which entities and areas. The key gets the intersection of both.
  • Business Central deletions are never available through the API.
  • Every request is recorded in the Usage log of the Admin Center (kept 90 days) without the key or the request body.
Was this page helpful?

On this page