Skip to main content
A project is the top-level container in GetRequest. Every endpoint you create lives inside a project, and every project gets its own unique URI that appears in the URL of every endpoint it contains. Projects let you keep traffic cleanly separated across environments without any overlap.

​
What Is a Project?

When you create a project, GetRequest assigns it a project URI — a short, randomly generated string like ddfkU760XMs2z7te. That URI is baked into every endpoint URL under the project:
Because the URI is part of the URL, requests destined for one project can never accidentally reach another. Your dev webhooks stay in dev, your production traffic stays in production, and your logs never intermingle.

​
The Project URI

The project URI identifies your project at the routing level. It is not a secret — it appears in every endpoint URL you share with webhook providers, API clients, or teammates.

Where to find it

Open your project in the dashboard and look in Settings → Project URI. You can copy it directly from there.

How it's used

Every endpoint URL under your project starts with https://e.getrequest.io/{project_uri}/. It routes incoming requests to the correct project before the slug selects the endpoint.
The project URI routes requests to the right project. Your API key authenticates you as the owner of that project. These are two separate values with different purposes — keep your API key private, but you can freely share endpoint URLs that contain the project URI.

​
The API Key

Your API key grants programmatic access to GetRequest — for example, creating or updating endpoints via the API. One API key works across all of your projects; you don’t need a separate key per environment. To find your API key, go to Settings → API Key in the dashboard.
Treat your API key like a password. Anyone who holds it can create, modify, or delete endpoints across all of your projects. If you suspect it has been compromised, regenerate it immediately (up to 6 times per hour).

​
Using Multiple Projects for Environments

The most common pattern is one project per environment. Each project gets its own URI, so traffic is fully isolated:
1

Create a project per environment

In the dashboard, create three projects: one for dev, one for staging, one for production. Note the project URI for each.
2

Configure your integrations

Point each environment’s webhook URLs and API clients at the corresponding project’s endpoint URLs.
3

Promote endpoints, not traffic

When an endpoint is ready for production, create the same slug in your production project and switch the action to Forward. Your dev project stays untouched.
You can mirror your endpoint structure across projects — using identical slugs in dev, staging, and prod — so the only difference in each environment’s configuration is the project URI segment of the URL.

​
Team Access

GetRequest accounts are currently single-user. If you need to share request details with a teammate, use the Share feature (Pro) to generate a public read-only link to any log entry. Teammates can view the full request and response without needing a GetRequest login. Multi-user team access is coming soon. In the meantime, Share links are the recommended way to collaborate — they expose only the specific log entry you choose to share, with no access to your endpoints or settings.