Activate an Incomplete Signup
POST/partner/v2/signup/activate
Creates a user in the organization previously created in /partner/v2/signup. This completes the signup
process if you did not pass in user details to /partner/v2/signup. Calling this endpoint if the signup
process has been completed will result in a 409 Conflict error.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 429
- 500
Successful signup activation. User is being created.
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.