Skip to content
  1. Docs
  2. Build With RoxyAPI
  3. Postman and Bruno

Astrology API Postman and Bruno collections

Import a RoxyAPI OpenAPI spec, set one header, hit Send. Time to ship: 2 minutes.

Test every RoxyAPI endpoint without writing code. Import our OpenAPI specs into Postman or Bruno and make live API calls in under a minute.

What you can build with this

  • Interactive API exploration across all 18 RoxyAPI domains
  • Request chains (geocode a city, then post the chart with the result)
  • Pre-configured collections teammates can fork and reuse
  • Local-first, Git-friendly API workspaces via Bruno
  • Quick-and-dirty endpoint testing before wiring a feature in code

What you need, 30 seconds

  1. A RoxyAPI key. Get your API key.
  2. Postman or Bruno installed.

Step 1, import the spec

Every RoxyAPI domain has a live OpenAPI spec you can point any API client at.

OpenAPI spec URLs

DomainURL
Western Astrologyhttps://roxyapi.com/api/v2/astrology/openapi.json
Vedic Astrologyhttps://roxyapi.com/api/v2/vedic-astrology/openapi.json
Forecasthttps://roxyapi.com/api/v2/forecast/openapi.json
Human Designhttps://roxyapi.com/api/v2/human-design/openapi.json
Chinese Astrologyhttps://roxyapi.com/api/v2/chinese-astrology/openapi.json
Feng Shuihttps://roxyapi.com/api/v2/feng-shui/openapi.json
Numerologyhttps://roxyapi.com/api/v2/numerology/openapi.json
Tarothttps://roxyapi.com/api/v2/tarot/openapi.json
Biorhythmhttps://roxyapi.com/api/v2/biorhythm/openapi.json
I Chinghttps://roxyapi.com/api/v2/iching/openapi.json
Crystalshttps://roxyapi.com/api/v2/crystals/openapi.json
Dreamshttps://roxyapi.com/api/v2/dreams/openapi.json
Angel Numbershttps://roxyapi.com/api/v2/angel-numbers/openapi.json
Locationhttps://roxyapi.com/api/v2/location/openapi.json

Combined spec (all 18+ domains at once): https://roxyapi.com/api/v2/openapi.json.

Postman

Option A, fork from the public workspace.

CollectionPostman link
Western AstrologyOpen in Postman
Vedic AstrologyOpen in Postman
TarotOpen in Postman
NumerologyOpen in Postman
I ChingOpen in Postman
DreamsOpen in Postman
CrystalsOpen in Postman
Angel NumbersOpen in Postman
LocationOpen in Postman

Or browse the full RoxyAPI Postman workspace. Click Fork to copy a collection into your workspace. Forked collections pull updates when we add new endpoints.

Option B, import from OpenAPI.

  1. Open Postman and click Import.
  2. Select Link and paste any spec URL from the table above.
  3. Postman converts the spec into a ready-to-use collection.

Bruno

Bruno is an open-source API client that stores collections as plain files. Git-friendly.

  1. Open Bruno and click Import Collection.
  2. Select OpenAPI V3 Spec.
  3. Paste any spec URL from the table above.
  4. Bruno generates a local collection with every endpoint ready to call.

Step 2, set the auth header

RoxyAPI uses X-API-Key, not Authorization: Bearer.

Postman

  1. Click Environments in the sidebar.
  2. Click Create Environment, name it "RoxyAPI".
  3. Add two variables:
VariableValueType
baseUrlhttps://roxyapi.comdefault
apiKeyyour API keysecret
  1. Select the collection > Authorization tab. Set:
    • Type: API Key
    • Key: X-API-Key
    • Value: {{apiKey}}
    • Add to: Header

Every request in the collection inherits this auth.

Bruno

  1. Right-click the collection > Settings.
  2. Under Auth, choose API Key.
  3. Set Key to X-API-Key, Value to your API key.

All requests inherit the header.

Do not share your environment file. The apiKey variable contains your secret key. Postman marks it as secret, but always verify before exporting. Bruno .bru files are plain text. If you commit them, use an env variable or .gitignore the secrets file.

Step 3, hit Send

Pick any endpoint from the imported collection. POST endpoints ship with example request bodies. Modify values, hit Send, see real API responses.

Starter endpoints to try first:

Gotchas

  • Auth header is X-API-Key, not Authorization: Bearer. Most API clients default to Bearer. Override it explicitly.
  • The base URL arrives complete. A domain spec declares its full server, https://roxyapi.com/api/v2/{domain}, and its paths hang off that, so the collection variable your client creates on import is ready to send.
  • POST endpoints always send JSON. Content-Type: application/json. Empty body is OK for seed-optional endpoints (daily tarot, daily hexagram).
  • Timezone accepts IANA strings or decimals on chart endpoints. Prefer "America/New_York".
  • Error shape is { error, code, doc_url }. No { success: false } wrapper. If you see 401, check the header name and the key.

FAQ

Which client should I use?

Postman if you want cloud sync, team sharing, and auto-updates from our public workspace. Bruno if you prefer open source, local-first, Git-friendly collections. Both work equally well.

Do I need a Postman account?

A free account is needed to fork collections and use environments. Importing from an OpenAPI URL works without an account, but you lose auto-updates.

Can I use Insomnia, HTTPie, Thunder Client, REST Client?

Any tool that imports OpenAPI 3.0 works. Use the same spec URLs above.

Where do I get an API key?

Get your API key. Every plan includes every domain, and the key is live the moment checkout completes.

What to build next

  • The API reference is a Scalar-rendered live playground. Paste your key to test any endpoint.
  • The SDK docs turn working curl calls into typed TypeScript, Python, PHP, C#, or Go code.
  • The MCP setup is the agent-first alternative. Point a coding agent like Claude Code, Cursor, or Copilot at the keyless docs server and it crafts the request for you, no manual building. Runtime agents on ChatGPT, Claude Desktop, Gemini, or n8n use the per-domain servers for live calls.