factory.app valid
Factory Sales API
Create and read sales orders and quotes, customers, and the supporting product catalogue, for your company.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T19:09:48.358Z. Cached copy · Source on factory.app
# Factory Sales API
> Create and read sales orders and quotes, customers, and the supporting product catalogue, for your company.
JSON over HTTPS at `https://api.factory.app/v1`. One bearer token per company. 59 operations across 12 services. Every page below is also available as Markdown by appending `.md`.
## Getting started
- [Factory API — sales orders, quotes and catalogue](https://developer.factory.app/index.md): Create and read sales orders, quotes, customers and the supporting product catalogue. JSON over HTTPS, one bearer token, scoped to your company.
- [Quickstart](https://developer.factory.app/quickstart.md): Four calls from API key to a written order: confirm the key, resolve a customer, find a product, then create a draft order.
- [Authentication](https://developer.factory.app/authentication.md): One bearer token in the Authorization header, scoped to a single company. No OAuth flow, no request signing, no query-string key.
- [Core concepts](https://developer.factory.app/concepts.md): Money as micros, 64-bit numbers as strings, type-prefixed ids, enum names, pagination and idempotency — read once, and the reference is obvious.
- [Field filtering](https://developer.factory.app/filtering.md): Trim responses to the fields you need with fields and excludeFields — camelCase names, dot paths into nested objects and across arrays, unknown names ignored rather than rejected.
- [Errors and status codes](https://developer.factory.app/errors.md): The validation-failure envelope, the stable error codes worth branching on, and the HTTP status codes and error types the API returns.
- [API conventions](https://developer.factory.app/conventions.md): The request-level rules: authentication and scoping, the error envelope and its types, rate limits, field filtering, and webhook deliveries.
## Guides
- [Push an order in from another system](https://developer.factory.app/guides/push-an-order-in.md): Take an order from a CRM, ERP or spreadsheet and land it on the floor: resolve the customer, build the lines, write it once safely, recover from a rejection.
- [Resolve customers and catalogue](https://developer.factory.app/guides/resolve-customers-and-catalogue.md): Nothing on a sales document is written by name. How to resolve customer ids, search the catalogue, and pick the right id out of four that look alike.
- [Keep another system in sync](https://developer.factory.app/guides/keep-in-sync.md): Build a poller on the change feed with an updatedSince checkpoint, let webhook deliveries trigger it, and reconcile quotes that become orders.
- [Build a flashing line](https://developer.factory.app/guides/build-a-flashing-line.md): Put a hand-drawn flashing on an order, worked end to end: the cut list, the drawing geometry, the girth, bend and length figures you compute yourself, the write, and the SVG upload.
## Reference
- [API reference](https://developer.factory.app/reference.md): Every operation in the Factory Sales API v1, grouped by service and g
…
Machine-readable: GET /v1/resolve?q=factory.app · GET /v1/domain/factory.app · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage factory.app, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for factory.app:
1. POST https://agentwebmap.com/v1/sites/factory.app/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://factory.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/factory.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/factory.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.