Skip to main content
Create
curl --request POST \
  --url https://api-staging.genuka.com/2023-11/developer/apps \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "callback_url": "http://localhost:3001/api/callback",
  "description": "Create you website from some starter templates",
  "medias": [
    {
      "collection_name": "logo",
      "src": ""
    }
  ],
  "name": "Genuka Templates",
  "privacy_policy_url": "https://genuka.com/privacy-policy",
  "redirect_url": "http://localhost:3001",
  "scopes": [
    "customer.*",
    "company.*",
    "products.*"
  ],
  "support_email": "[email protected]",
  "terms_of_service_url": "https://genuka.com/terms",
  "webhook_url": "http://localhost:3001/api/webhook"
}
'
This endpoint allows developers to create a new application on Genuka.
When creating an app, you must provide the following details:

Parameters

  • Application Name
    A unique and descriptive name for your application. This name will appear in the developer dashboard and may also be visible to end-users when requesting permissions.
  • Description
    A short summary of what your application does and how it will use the Genuka API. This helps the Genuka team review your request and helps users understand the purpose of your integration.
  • Public URL
    The official website of your application. This should be a valid URL where users can learn more about your app. For example, it might be your product’s homepage or landing page.
  • Support Email
    An active email address that users can contact if they experience issues with your app. This is also used by the Genuka team for communication during the review and approval process.
  • Redirect URL
    The URL where users are redirected after open app on Genuka.
  • Callback URL
    The endpoint in your application that will handle authentication responses from Genuka. Typically, this is where your app exchanges the authorization code for an access token.
  • Scopes
    A list of permissions your application is requesting (e.g., access to user profile, email, or other resources). Each scope should be strictly necessary for your integration to function. Requesting unnecessary scopes may cause your app to be rejected during the review.
  • Webhook Endpoints (optional)
    If your application needs to receive real-time updates from Genuka (e.g., when a product’s is created or a user updates their account), you can provide one or more webhook URLs. These endpoints must be secure and publicly accessible.

Would you like me to also add an example request/response (in JSON) for this endpoint so it looks like a full API reference?

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

x-company
string
Example:

"{{DeveloperCompanyId}}"

Body

application/json
callback_url
string
Example:

"http://localhost:3001/api/callback"

description
string
Example:

"Create you website from some starter templates"

medias
object[]
Example:
[{ "collection_name": "logo", "src": "" }]
name
string
Example:

"Genuka Templates"

privacy_policy_url
string
Example:

"https://genuka.com/privacy-policy"

redirect_url
string
Example:

"http://localhost:3001"

scopes
string[]
Example:
["customer.*", "company.*", "products.*"]
support_email
string
terms_of_service_url
string
Example:

"https://genuka.com/terms"

webhook_url
string
Example:

"http://localhost:3001/api/webhook"

Response

200 - undefined