Postman
Skip the setup.
Every Vector Pro endpoint, already organised into folders, already pointed at the production API, already wired for bearer auth. Import it and send a request.
What you're importing
Postman is an API client: a visual way to build requests, keep them organised in collections, and share them with the rest of your team.
This collection is generated from the same source as the reference, so the request bodies, query parameters, and example values are the ones documented here — not a hand-maintained approximation that drifts.
No account is needed to import it. Use the desktop app or the web version.
Collection details
- Format
- Postman v2.1
- Folders
- 9
- Base URL
- api.builtfast.com/api/v1/vector
- Auth
- Bearer token
Three steps to a first request
- 1
Import the collection
Download the JSON and drop it into Postman — File → Import, or drag the file onto the sidebar.
postman.json → Postman - 2
Add your token
Open the collection's Authorization tab. It is already set to Bearer Token; paste your Vector Pro key into the Token field.
Collection → Authorization - 3
Send something
Open Sites → List Sites and hit Send. Every folder and request inherits the auth you just set.
Sites → List Sites → Send
How it's wired
- {{baseUrl}}
- The collection's one variable, preset to
https://api.builtfast.com/api/v1/vector. Requests append their own/api/v1/vector/…path, so override this only to aim at a different host. - Authorization
- Bearer auth is declared on the collection, not on each request. Set the token once and all 9 folders inherit it.
What's inside
The same 9 groups as the reference. Each links to its documentation.
Working with the collection
Use the Console — View → Show Postman Console prints the raw HTTP exchange. It is the fastest way to see why a request came back 422.
Save responses as examples — After a successful call, save the response. The collection then documents the shapes your own account actually returns.
Run a folder — The Collection Runner sends a whole folder in order, which is enough to exercise a create-deploy-verify workflow end to end.
Expect 202s — Site, environment, and deployment calls are asynchronous. They return 202 and finish later, so poll the resource or subscribe to a webhook.
Prefer a different format?
The same API, as browsable documentation or as an OpenAPI 3.1 spec.