Altru and CRM SKY APIs

Options

What needs to be done to improve support for the Infinity-based applications within the SKY API? I understand that partner developers aren't going to bother with the SKY API since they have access to much more powerful tools (Infinity SDK and SOAP API), but what are small developers supposed to do? We either need a much more complete SKY API endpoint set, or more general-purpose endpoints defined such as the SOAP API has, or simply given access to use the SOAP API. Otherwise, development for Altru will continue to be essentially nonexistent except through largely one-way solutions that utilize the OData links in Query.

And sure, there are good endpoints for working with constituents, but most other areas are pretty sparse or non-existent. And since Altru is not about constituents and prospects and relationships as much as it is about programs and the sale of tickets, the API is skewed in its coverage to favor Blackbaud CRM developers, who likely aren't using the SKY API at all. For Altru developers, we need endpoints to access ticketing, sales, group sales, programs, program events, itineraries, and so forth, because those are the areas that Blackbaud's Altru customers want solutions for.

Also, what is the purpose of defining an Altru endpoint that only takes an ID (as opposed to a name), but you refuse to give your developers access to feature metadata so we can know what the IDs are? I know some IDs can be found in the web address and sometimes buried in the page code, but I know some never get even that kind of exposure.

Like my clients, I am just looking for a solution, here.

Comments

  • @Bill Grimm Were you ever able to find a solution here? I'm also looking for an API method to access “program events”.

Categories