API Endpoint
- URL:
https://text-tad.droplinked.workers.dev/ - Method:
POST - Content-Type:
application/json
Authentication
To use the API, an API key is required. Contact Droplinked support to obtain your API key. Include it in the request headers as follows:- Header:
api-key - Value:
<YOUR_API_KEY>(provided by Droplinked)
Request Format
The API accepts a JSON payload with the following fields:Request Body
| Field | Type | Required | Description |
|---|---|---|---|
command_name | String | Yes | Must be set to "description" for description generation. |
title | String | Yes | The product title to base the description on. |
description | String | No | Optional existing description to enhance (can be empty). |
tone | String | Yes | The desired tone (e.g., “wellness-focused”, “tech-savvy”). |
Example Request Body
Response Format
- Content-Type:
text/plain - Response: A plain text string containing the enhanced description, formatted with:
- 3-5 bullet points using hyphens (
-) - 1-2 relevant emojis maximum
- No JSON wrapper, Markdown, or additional explanations
- 3-5 bullet points using hyphens (
Example Response
Guidelines for Generated Descriptions
The API adheres to these rules:- Direct Output: Only the enhanced description is returned—no JSON, formatting markers, or explanations.
- Structure: Descriptions consist of:
- An introductory sentence (optional, based on input).
- 3-5 bullet points starting with hyphens (
-).
- Content:
- Incorporates SEO keywords derived from the
titleanddescription. - Uses clear, benefit-driven language tailored to the specified
tone. - Includes 1-2 relevant emojis maximum.
- Incorporates SEO keywords derived from the
- Restrictions:
- No JSON syntax or wrappers.
- No Markdown (e.g.,
**,#). - No technical notes or extraneous text.
JavaScript Example
Below is an example of how to use the Product Description Generator API in JavaScript with thefetch API:
Error Handling
- Invalid API Key: Returns an error message (e.g., “Unauthorized”).
- Missing Required Fields: If
command_name,title, ortoneis missing, the API may return an error or unexpected output. - Network Errors: Handle errors in the
.catchblock of thefetchcall.
Example Error Output
Best Practices
- Tone Selection: Choose a tone that matches your target audience (e.g., “casual”, “luxury”, “tech-savvy”).
- Input Description: Provide an optional
descriptionto give the API more context, though it works fine with just atitle. - Consistency: Use consistent tones across related products for brand coherence.
- Testing: Experiment with different titles and tones to refine the output.