Feat: This PR introduces a React-based API Testing Tool that allows users to build, send, and test HTTP requests directly within ReactPlay.

[Abhrxdip]

The feature enables developers to configure request methods, URLs, headers, and request bodies, send API calls, and view formatted responses including status and payload. It aims to simplify API debugging and learning workflows in an interactive and user-friendly way.

No external dependencies were added beyond existing project tooling.

Fixes # (issue)

Type of change

Bug fix (non-breaking change which fixes an issue)

New feature (non-breaking change which adds functionality)

Breaking change (fix or feature that would cause existing functionality to not work as expected)

This change requires a documentation update

How Has This Been Tested?

Tested locally using the development server

Verified API requests using multiple HTTP methods (GET, POST)

Tested valid and invalid request scenarios

Verified loading, success, and error states

Confirmed responsive behavior across screen sizes

Ensured no console warnings or runtime errors

Checklist:

I have performed a self-review of my own code

I have commented my code, particularly in hard-to-understand areas

I have made corresponding changes to the documentation

My changes generate no new warnings

I have added tests that prove my feature works

New and existing unit tests pass locally with my changes

Any dependent changes have been merged and published in downstream modules

Screenshots or example output

[netlify]

‼️ Deploy request for reactplayio rejected.

Name	Link
🔨 Latest commit	a30be9d

[github-actions]

Hey! contributor, thank you for opening a Pull Request 🎉.

@reactplay/maintainers will review your submission soon and give you helpful feedback. If you're interested in continuing your contributions to open source and want to be a part of a welcoming and fantastic community, we invite you to join our ReactPlay Discord Community.
Show your support by starring ⭐ this repository. Thank you and we appreciate your contribution to open source!
Stale Marking : After 30 days of inactivity this issue/PR will be marked as stale issue/PR and it will be closed and locked in 7 days if no further activity occurs.