Only company admins can generate API keys. If you are unsure whether you have the correct permissions, follow the steps below to check.
Before You Begin
Everything you need to know before making your first G360 API call.
What is Granite360?
Granite 360 is Granite Telecommunications’ all-in-one portal that unifies network monitoring, service management, and field technician dispatch, giving enterprises a single hub to oversee their voice, data, and cellular services across every location.
The Granite 360 APIs extend this platform to developers, enabling you to programmatically access the same capabilities through a collection of RESTful endpoints.
The Four API Pillars
The G360 API is organized into four pillars, each covering a distinct part of the connectivity lifecycle:
Accessexpress
Internet service quoting and ordering. Search for available broadband and DIA products at any location, compare offerings, and provision services programmatically.
Techexpress
Field technician dispatch. Create service tickets to send technicians to customer sites for installations, site audits, equipment repairs, and smart hands support.
NOCexpress
Network issue ticketing. Report and track network incidents through Granite's Network Operations Center, from ticket creation through resolution.
Inventory
Service and account visibility. Query your active services, monitor service changes, retrieve account metrics, and get a complete view of your connectivity portfolio.
Authentication
The Granite360 API uses OAuth 2.0 Bearer tokens for authentication. All API requests must include a valid access token in the Authorization header.
To authenticate, you will need to:
1. Obtain your API credentials: Generate a Client ID and Client Secret from the Granite360 portal.
Note
How to check your permissions:
- Log in to your company page on Granite360
- On the home page, next to your name, look for the three dots menu
- Click My Settings
- Check your Roles and permissions
If you are not a company admin:
- Reach out to your company admin to generate keys on your behalf
- Or reach out to the Granite team to update your access
2. Exchange credentials for an access token: Use the OAuth 2.0 client credentials flow to request a Bearer token.
3. Include the token in all requests: Pass the token in the Authorization: Bearer {token} header.
Follow the step-by-step instructions in the Authentication section.
Scopes
Each pillar is protected by its own OAuth scope. When requesting an access token, specify the scope(s) for the pillar(s) your integration needs:
| Pillar | Scope |
|---|---|
| Accessexpress | urn:grt:accessexpress |
| Techexpress | urn:grt:techexpress |
| NOCexpress | urn:grt:nocexpress |
| Inventory | urn:grt:inventory |
| Accounts | urn:grt:accounts |
If your integration needs access to multiple pillars, request them space-separated in the token call:
Request only the scopes your integration actually uses. You can always request additional scopes later as your integration expands.
Environments
Granite360 provides two environments for API development:
| Environment | Purpose | Access |
|---|---|---|
| Production | Live environment with real data and services | Available immediately after generating API keys |
| Test | Sandbox environment for safe integration testing | Requires setup by G360 support team |
Switching between environments: In the documentation header you will see a Staging / Production toggle. Staging is the same sandbox as the Test environment above; Production is live. Choosing an option automatically updates all URLs and code samples on the page to match that environment.
Using the Production environment
Follow the Getting Started guide in the next section. No additional setup required.
Using the Test environment
Contact G360 support to get set up. Our team will create your company account in the sandbox and send invitations to your developers. Once provisioned, you will receive test credentials that work against the sandbox endpoints.
When should you use the Test environment?
We recommend using the Test environment when:
- You are implementing order flows (Accessexpress) and want to validate end-to-end quoting and ordering without creating real orders
- You are building ticketing integrations (Techexpress or NOCexpress) and need to verify your workflows before dispatching real technicians or filing live NOC tickets
- You are onboarding a new team and want developers to experiment freely without impacting production data
For read-only operations like inventory queries or quote lookups, the Production environment is generally safe to use during development.
Last updated on