Name Request Service API
Overview
The Name Request service can be used to submit, track and manage a NameRequest. NameRequests are used to reserve, and get approval, to use a name in the Business Registry.
Note: All requests must include a BC Registries issued API key and an Account ID.
View the API
View the definition and select a path to try it out. To submit a request, you will need an API key and an account ID, which you can get by completing the account setup process. To set your session API key, click on the top, right AUTHORIZE button and under API Key Auth enter your key value. Click on AUTHORIZE, then OK.
Fees
All fees are specified within the regulations. See our fee schedule for details
API Quick Reference
| Endpoint Path | Description |
|---|---|
| GET /namex/api/v1/statistics/ | Get NR Processing Time (regular wait time, ​priority wait time, auto approved count). |
| POST /namex/api/v1/payments/fees | Get NR Fees you must pay for a specified filing type code in Name Request. |
| GET /namex/api/v1/name-analysis/ | Analyze a proposed BC business name to identify structural or designation issues. |
| GET /namex/api/v1/documents:restricted_words | Scan a proposed BC business name for restricted terms that are prohibited or require written consent. |
| GET /namex/api/v1/exact-match | Retrieve BC business names that exactly match the provided name. |
| GET /namex/api/v1/requests/synonymbucket/{name}/{advanced_search} | Retrieve BC business names similar to the provided name to identify potential conflicts. |
| POST /namex/api/v1/namerequests/ | Creates a new Name Request and returns a provisional L-number in PENDING_PAYMENT status. |
| GET /namex/api/v1/namerequests/ | Retrieves the details of a Name Request. Requires the NR number along with the applicant's email or phone number. |
| PATCH /namex/api/v1/namerequests/{nr_id}/{nr_action} | Performs an action on a Name Request. The nr_action should be one of EDIT, CANCEL, REQUEST_REFUND. |
| GET /namex/api/v1/namerequests/{nr_id}/result | Returns the Name Request results report as a PDF file. The Name Request must be in an approved, consumed, expired, or rejected state. |
| POST /namex/api/v1/payments/{nr_id}/{payment_action} | Creates a payment invoice for the Name Request. The payment_action should be one of CREATE, UPGRADE, REAPPLY, RESUBMIT. |
| GET /namex/api/v1/payments/{nr_id} | Retrieves all payment records from SBC Pay that are linked to the specified Name Request. |
| POST /namex/api/v1/payments/{payment_id}/receipt | Generate a PDF receipt for the specified payment. |
Date and Date Time Formats
Dates, without a time are considered a fixed date regardless of timezone. For regulatory purposes all dates are acted upon in 'Pacific' time.
All data with times are in UTC, both submitted and retrieved via the API. These can be displayed in local time for end users. For legal purposes the effective and legal dates are in the 'Pacific' timezone.
API Version History
| Date | Version | Description |
|---|---|---|
| 2018-06-25 | 0.0.0 | Namex Pre-Refactor Release |
| 2019-02-04 | 1.0.4 | UI Focus Release |
| 2021-07-29 | 1.1.0 | Name Request Go-Live Enhancements Release |
| 2025-02-12 | 1.2.21 | NRO Decommision Release |
| 2025-04-09 | 1.2.34 | GCP Migration Release |
Additional Resources
- Refer to the BC Registry site to open an account and see all the Registry services.
- Refer to the Discourse Community site to answer any API and service related questions.
Page History
Updates of note to this page are recorded here.
| Date | Description |
|---|---|
| 2025-07-15 | Added Namex Api Spec |
| 2026-01-18 | Validated Names API Documentation |