exa-studio / exa-studio/ApiVault
[NEW API] Nexscope Ecommerce Data and Creative APIs
- Dominant language
- JavaScript
- Stars
- 702
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
### API Information
**API Name:** Nexscope Ecommerce Data and Creative APIs
**Description:** Nexscope provides ecommerce data, product video, and creative APIs that help sellers and developers research products and markets, analyze marketplace and advertising insights, and create ecommerce content.
**Category:** Shopping
**What Auth is used (ex: Api Key):** API Key
**HTTPS:** true
**CORS:** false
**API Link:** https://www.nexscope.ai/api-docs?co-from=APIapivault
**OpenAPI:** https://api.nexscope.ai/openapi.json
**Website:** https://www.nexscope.ai
**Logo:** https://www.nexscope.ai/favicon.png
**Support:** service@nexscope.ai
### Why we should integrate this API on the listing?
Nexscope gives ecommerce sellers, developers, and product teams programmatic access to marketplace intelligence and creative workflows. It covers product and market research, keyword and advertising insights, pricing and ranking data, product images, product video, and other focused ecommerce capabilities through documented REST APIs.
Nexscope APIs use account-based credits. Actual usage varies by endpoint and workload. Users can create a Nexscope account to view current estimates, available credits, and API access.
### Submission note
The ApiVault website submission form could not be completed because Google sign-in currently returns `invalid_client` and sends the placeholder client ID `GOOGLE_CLIENT_ID`. This issue uses ApiVault's official "Add Your API" GitHub template as the alternative submission channel.
### Thanks for the contribution ❤️
Contributor guide
Research direction
Review the repository's existing API listings and the official "Add Your API" template, then inspect the Nexscope API documentation and OpenAPI link provided here. Add the Nexscope details in the matching listing format, preserving the authentication, HTTPS, category, logo, and support information, and verify that the links and required fields are valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100