We are happy to share that Jasper now provides two new abilities via the API:
In addition, API users will be able to apply their style guide during generation, meaning they can generate content and apply style rules in the same request.
We added the ability to optionally apply a style guide to any /command
or /templates
request. This is as simple as adding the styleId
as a parameter in the body (similar to tone). For example, with commands:
{
"inputs": {
"command": "Create a blog recommending the top songs to play at a 4th of July party.",
"toneId" : "ton_4ddeaaae1c38450abe066fa7ace8f357",
"styleId" : "sty_6ad0d3704d8341b48ab2e3683d9d03b2"
}
}
You can learn more about how to retrieve & apply style guides on our API documentation portal.
We are happy to share that Jasper now provides two new abilities via the API:
In addition, API users will be able to apply their style guide during generation, meaning they can generate content and apply style rules in the same request.
We added the ability to optionally apply a style guide to any /command
or /templates
request. This is as simple as adding the styleId
as a parameter in the body (similar to tone). For example, with commands:
{
"inputs": {
"command": "Create a blog recommending the top songs to play at a 4th of July party.",
"toneId" : "ton_4ddeaaae1c38450abe066fa7ace8f357",
"styleId" : "sty_6ad0d3704d8341b48ab2e3683d9d03b2"
}
}
You can learn more about how to retrieve & apply style guides on our API documentation portal.