Skip to content
Caspio Ideabox

Caspio

Welcome to Caspio Ideabox. We love to hear your improvement ideas.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

3 results found

  1. Provide pagination information in response headers for REST API requests

    As noted in a previous post (link: http://ideabox.caspio.com/forums/164206-caspio-bridge/suggestions/13926690-implement-paginated-responses-for-rest-api-request) that has since been marked as "completed," we now have the ability to make paginated requests when using the REST API, but no useful pagination information is sent back (e.g., links for next, prev, first, last). Since we are rate-limited at 1000 items per request, it would be very helpful to know how many pages of data we might need to request to get "everything" (e.g., something similar to how more pagination info is sent back in the Link header like in this API for Game of Thrones: https://anapioficeandfire.com/Documentation ).

    Note:…

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Add update function to Zapier API

    Currently can use a Zap to add a record. Would be nice to be able to update existing records with a return code of success or failure. Other functions like GET to query data before update is nice but not absolutely necessary.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    started  ·  1 comment  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Integrate Payment Processing as a standard feature

    Payment processing should be integrated within Caspio as a standard feature. You could limit the number of payment processors to Paypal, Google Checkout and a couple of others but this should absolutely be standard. Why is this an "add-on"?

    93 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  API  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

Caspio

Categories

Feedback and Knowledge Base

(thinking…)