Fix Python code sample JSON body

[rodrcastro]

When sending a JSON body in the request, it should use json. This PR changes it to make the code sample request correct.

[linear[bot]]

RND-6538 JSON body in Python code sample is not being set

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 631cecc826f2f96dfde42ba4dedf755810e737cc

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions[bot]]

Summary of the deployments:

Version 1 (production)

Version	URL	Status
Latest commit	https://1127a3ef.gitbook-open.pages.dev	✅
PR	https://pr2976.gitbook-open.pages.dev	✅

Version 2 (experimental)

Version	URL	Status
Vercel	https://gitbook-v2-6ptpzjtbs-gitbook.vercel.app	✅
Cloudflare	https://f2d4c641-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	v1	v2
GitBook	https://1127a3ef.gitbook-open.pages.dev/docs.gitbook.com	https://gitbook-v2-6ptpzjtbs-gitbook.vercel.app/url/docs.gitbook.com
E2E	https://1127a3ef.gitbook-open.pages.dev/gitbook.gitbook.io/test-gitbook-open	https://gitbook-v2-6ptpzjtbs-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci[bot]]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v1 (Inspect)	⚠️ Changes detected (Review)	13 changed	Mar 19, 2025, 8:56 PM
customers-v2 (Inspect)	⚠️ Changes detected (Review)	12 changed	Mar 19, 2025, 8:56 PM
default (Inspect)	⚠️ Changes detected (Review)	31 changed	Mar 19, 2025, 8:57 PM
v2-vercel (Inspect)	⚠️ Changes detected (Review)	22 changed	Mar 19, 2025, 9:00 PM

[nolannbiron]

@rodrcastro We are using data instead of json to handle any content type.

If you want to send text/csv, text/plain or multipart, you can’t use json, it’s just a shorthand that implicitly sets the content type to application/json.

data works with any content type, as long as you specify it in the headers.

[nolannbiron]

but we can set it to json for application/json, if customers really want to see this instead of data

[nolannbiron]

@SamyPesse @rodrcastro I've updated the code to handle json={} for application/json and data={} for others content type, I made this because we had a past issue to handle multiple content type