Signup an Organization on behalf of a Customer
POST/partner/v2/signup
Create an organization for a customer. You must pass in either an entitlement object reference (a url to
a previously created entitlement) or entitlement details. If you pass in an entitlement object reference, we will link with the
created entitlement. If you pass in the entitlement details, we will create the entitlement with the organization
in a single transaction. If you pass in user details (email, given name, and family name), we will
create a user as well. If you do not pass in user details, you MUST call /partner/v2/signup/activate
with user details to complete signup.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 429
- 500
Successful signup.
Bad Request
Response Headers
The unique identifier for the API request.
The request lacks valid authentication credentials for this resource.
Response Headers
The unique identifier for the API request.
The unique identifier for the API request.
Basic error="invalid_key", error_description="The API Key is invalid"The access credentials were considered insufficient to grant access
Response Headers
The unique identifier for the API request.
The request is in conflict with the current server state
Response Headers
The unique identifier for the API request.
Resource URI of conflicting resource
Rate Limit Exceeded
Response Headers
The unique identifier for the API request.
The maximum number of requests you're permitted to make per time period.
The number of requests remaining in the current rate limit window.
The relative time in seconds until the current rate-limit window resets.
Important: This differs from Github and Twitter's same-named header which uses UTC epoch seconds. We use relative time to avoid client/server time synchronization issues.
The number of seconds to wait until the rate limit window resets. Only sent when the rate limit is reached.
Oops, something went wrong!
Response Headers
The unique identifier for the API request.