Get Organization Info
GET/organization
This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account.
Responses
- 200
- 401
Returns organization details
- application/json
- Schema
- Example (from schema)
Schema
distribution_account
object
required
The address of the distribution account, present when the account type is STELLAR
.
The ID of the Circle wallet, present when the account type is CIRCLE
.
Possible values: [DISTRIBUTION_ACCOUNT.STELLAR.ENV
, DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT
, DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT
]
The type of the distribution account.
Possible values: [ACTIVE
, PENDING_USER_ACTIVATION
]
DEPRECATED! Please refer to distribution_account.address instead.
Enables multi-user approval workflow for disbursements
The amount of days that the SDP will wait to resend the invitation SMS to the receivers that have not registered. If 0
, that means the resending invitation SMS feature is disabled.
The amount of days that the SDP will wait to cancel a payment that is waiting for the receiver to register. If 0
, that means the payment cancellation feature is disabled.
The link to the organization privacy policy
The custom SMS message template set for the registration invite. The default
message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).
The custom OTP message template set to send OTP code to the receiver complete the registration flow. The default
message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.OTP}} which is the OTP code to send to the receiver complete the registration flow (in case this is not present in the message, it's automatically appended at the end).
{
"name": "Stellar Aid",
"logo_url": "https://stellar-disbursement-platform-backend-dev.stellar.org/organization/logo",
"distribution_account": {
"address": "GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL",
"circle_wallet_id": "1000646072",
"type": "DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT",
"status": "ACTIVE"
},
"distribution_account_public_key": "GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL",
"timezone_utc_offset": "+00:00",
"is_approval_required": true,
"sms_resend_interval": 5,
"payment_cancellation_period_days": 5,
"privacy_policy_link": "https://stellar.org/privacy-policy",
"sms_registration_message_template": "You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register.",
"otp_message_template": "{{.OTP}} is your {{.OrganizationName}} phone verification code."
}
Unauthorized
- application/json
- Schema
- Example (from schema)
- Example
Schema
extras
object
{
"error": "Not authorized",
"extras": {
"status": 401,
"message": "Not authorized"
}
}
{
"error": "Not authorized",
"extras": {
"status": 401,
"message": "Not authorized"
}
}