Aglyn REST API
API by Aglyn · rest
The customer REST API. Authenticate with an API key as a bearer token, or with the access token an app gets by signing in (the connector scheme); every response is JSON. MCP server The same API is served as Model Context Protocol tools at https://app.aglyn.com/api/mcp (Streamable HTTP). Any MCP client can connect with an API key, or sign in: an unauthenticated call is answered 401 with WWW-Authenticate: Bearer resource_metadata="https://app.aglyn.com/.well-known/oauth-protected-resource/api/mcp" (RFC 9728), and the authorization server is described at https://app.aglyn.com/.well-known/oauth-authorization-server (RFC 8414). Its server card is https://app.aglyn.com/api/mcp/server-card. Pagination Every list returns { object: "list", data, next_cursor, has_more } and pages with an opaque cursor. has_more is the only termination signal. Several lists filter rows out after the read, so a page of 100 can come back with 60 rows — or none — and has_more: true.…
Endpoint: https://app.aglyn.com/api
Verification: observed. Source: crawl.
Capabilities (88)
- Describe the API
- List activities
- Log an activity
- Get an activity
- Delete an activity
- List companies
- Add a company
- Get a company
- Update a company
- Delete a company
- List contacts
- Add a contact
- Get a contact
- Update a contact
- Delete a contact
- Merge two contacts
- List datasets
- Create a dataset
- Get a dataset
- Update a dataset
- Delete a dataset
- List a dataset’s records
- Add a record to a dataset
- Get a dataset record
- Update a dataset record