canonical: https://jentic.com/apis/mightyrep.com/mightyrep # MightyRep API Jentic publishes the only available OpenAPI specification for MightyRep API, keeping it validated and agent-ready. MightyRep is a sales rep CRM and field-team workflow tool; its REST API exposes 139 endpoints to manage organisations, users, contacts, products, orders, visits, samples, and the supporting reference data that field reps work with day to day. Authentication is by API key sent in the x-auth-token header. The endpoint surface covers full CRUD on the core sales objects plus logo and document attachment handling. ## For AI agents Manage organisations, contacts, users, products, orders, visits, and samples in a MightyRep field-sales CRM via API key authentication. ## Scope Does not handle marketing automation, payment processing, or rep mobile-app authentication - use for CRUD on field-sales organisations, users, contacts, products, and orders only. ## Capabilities - Create and search organisations in the MightyRep account hierarchy - Maintain a contact directory of users tied to each organisation - Upload and replace logo images on organisation records to keep branding current - Record sales visits and orders linked to organisations and contacts for territory reporting - Manage product catalog entries used in orders and sample drops - Pull lists of organisations or users for downstream analytics and routing agents - Delete obsolete records to keep the rep workspace and dashboards clean ## Use cases ### Field Rep Account Sync Sync organisations and contacts from a master CRM into MightyRep so field reps see the same accounts in their mobile workflows. The API handles full CRUD on organisations and users, and image upload for logos that reps recognise on their visit lists. Example prompt: For each new account in the master CRM, POST `/api/organisations` with name and address, then POST `/api/organisations/logo/{id}` to upload the brand logo. ### Sales Territory Reporting Pull all organisations and the rep-user assignments out of MightyRep to feed dashboards that show coverage by territory and identify under-visited accounts. The API exposes paginated lists across organisations and users to build a current snapshot. Example prompt: Fetch all organisations via GET `/api/organisations` and all users via GET `/api/users`, then group organisations by assigned user to produce a territory coverage report. ### Data Cleanup Automation When duplicates or stale records build up, an agent searches for matches by name and address, then deletes or merges entries via the organisation and user endpoints. This keeps reps focused on real accounts rather than ghost records. Example prompt: Search organisations matching a normalised name and address, keep the most recent record, and DELETE `/api/organisations/{id}` for the duplicates. ### Agent-Driven CRM Updates via Jentic Through Jentic, an agent manages MightyRep records using semantic search rather than reading API docs. The x-auth-token API key is held in your Jentic One instance and injected on each request, so the agent updates field-rep data without ever touching the secret. Example prompt: Use Jentic search 'create an organisation in mightyrep', load the schema for POST `/api/organisations`, and execute with the new account's name, address, and contact details. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/organisations` | Browse and search organisations | | POST | `/api/organisations` | Create a new organisation | | GET | `/api/organisations/{id}` | Get an organisation by id | | PATCH | `/api/organisations/{id}` | Partially update an organisation | | DELETE | `/api/organisations/{id}` | Delete an organisation | | POST | `/api/organisations/logo/{id}` | Upload an organisation logo | | GET | `/api/users` | Browse and search users | ## Key resources - **Organisations** — Create, search, update, and delete account records, including logo uploads - **Users** — Create, list, and manage user records within the MightyRep account - **Contacts** — Manage the contact directory linked to organisations - **Products** — Maintain the product catalog used in orders and samples - **Orders** — Record orders placed by reps against organisations ## Why Jentic - **Setup:** Wiring the MightyRep API by hand means reading its x-auth-token header scheme and finding the right call among many organisation, user, contact, product, and order operations yourself. Through Jentic you install once, import the MightyRep API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** MightyRep puts the organisation id in the URL path (`/api/organisations/{id}`), so a rule can pin your agent to specific organisations. You choose the operations it may call, so deleting an organisation with a DELETE is not included unless you add it. - **Credential handling:** Your MightyRep API key is stored once, encrypted, by your own Jentic One instance and injected into the x-auth-token header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an organisation in MightyRep' or 'list users', and Jentic returns the matching MightyRep operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **HubSpot CRM Contacts API** — Mainstream cloud CRM with deep marketing and sales features. - **Pipedrive API** — Pipeline-centric CRM popular with small sales teams. - **Salesforce API** — Enterprise CRM that often acts as the master record for accounts. ## FAQ ### Why is there no official OpenAPI spec for MightyRep API? MightyRep does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MightyRep API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the MightyRep API use? The API uses an API key sent in the x-auth-token header (the access-key security scheme in the spec). The key is generated inside the MightyRep account settings. Through Jentic, the key is stored in the encrypted vault and injected on each call without entering the agent's context. ### Can I upload a logo for an organisation through the API? Yes. POST `/api/organisations/logo/{id}` accepts an image upload and attaches it to the organisation record so reps see the brand mark in their lists and visit views. ### What are the rate limits for the MightyRep API? MightyRep does not publish public rate limits in the spec. Treat the API as rate-limited per token and back off on HTTP 429 responses; contact MightyRep support for negotiated limits when running large sync jobs. ### How do I create an organisation in MightyRep through Jentic? Run pip install jentic, search for 'create an organisation in mightyrep', load the schema for POST `/api/organisations`, and execute with the organisation name and address. Jentic injects your stored x-auth-token automatically. ### Does the API support partial updates? Yes. PATCH `/api/organisations/{id}` and PATCH `/api/users/{id}` accept partial bodies, so you can update only changed fields without re-sending the whole record. ### Can I limit what my agent is allowed to do with the MightyRep API? Yes. Because you run Jentic One yourself, your own rules decide which MightyRep operations and credentials the agent may use. Since the organisation id sits in the URL path, such as `/api/organisations/{id}`, you can pin the agent to specific organisations, and you choose the operations it may call, so a destructive DELETE `/api/organisations/{id}` is not available unless you add it. Read-only work like GET `/api/organisations` and GET `/api/users` can be allowed while writes such as POST or PATCH stay excluded.