> For the complete documentation index, see [llms.txt](https://docs.paystation.ng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paystation.ng/guides/environments.md). # Environments API keys carry an environment value. Use credentials created for the environment in which the request should run. ## Production ``` https://paystation.ng/api/v1 ``` Production requests may create real provider resources and process real funds. Test with controlled customer data and small amounts. ## Local development When running the Laravel application locally, the equivalent base URL is normally: ``` http://127.0.0.1:8000/api/v1 ``` Provider callbacks cannot reach localhost directly. Use a secure tunnel only during controlled testing, and never expose development secrets. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.paystation.ng/guides/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.