Mashery Support Portals Developer BlogRSS Feed
We have more exciting UI changes coming to the Control Center. Soon you will have a more visually appealing white background for the API Control Center instead of the traditional dark one. We hope this will provide a much better visual experience for you. We are making this change for several reasons:
- The color scheme matches with the rest of the products offered by TIBCO cloud services and provides a more unified UI experience.
- Feedback from a majority of customers indicated a preference towards a “lighter” application.
- It sets the stage for further enhancements to the product, including leveraging API oriented capabilities found in TIBCO Cloud Integration (http://cloud.tibco.com).
Below are the screenshots of the new user interface.
A while back, we announced the availability of the TIBCO Mashery Connector for TIBCO Simplr (blog post here). And we haven't stopped there! Over the past month, we've been working hard to make it easier to use as well as open up more data that can be pulled out of the Mashery V3 API. The enhancements are as follows:
- Export of package key data, with associated developer username and email
- Export of reporting data for Package Keys, including Package, Plan, API information and developer metadata
- Export of QPS data for Package Keys, including Package, Plan, API information and developer metadata
We are pleased to let you know about some exciting changes coming to your Control Center experience. We have introduced a new header and incorporated a few changes based on customer feedback. For the new header "Mashery Control Center" has been replaced with "TIBCO Mashery".
The area name is displayed on the right and clicking the area name would give additional information, such as the Area UUID. This is a quick and easy way to find the UUID of a given area. Next to the area name is an icon(?) that you can click to get area information, get access to the latest Control Center documentation or get information on how to contact support.
As always we are trying to make the product better and we have bigger changes coming to the Control Center especially with regards to the look and feel. Stay tuned for more product updates.
Mashery Local 3.1.1 is generally available for customer download on edelivery.tibco.com. The release includes greater access to networking system level commands for the Mashery Local administrator plus includes critical bug fixes.
We are super excited here at TIBCO Mashery to announce the release of our new feature: Distributed API Management. The feature adds group-aware role based access control to the Mashery product. Distributed API Management will allow users to create multiple organizations within the Control Center. Different assets such as Users, APIs and Packages can be assigned to an organization and managed independently of each other. Depending on which organization a user belongs to and what permission he or she has, they will be able to perform certain operations and view certain assets. Currently we have the roles of Admin, API Manager, Community Manager and a Reports User within an organization that can be assigned to a Control Center User.
We have also provided a new way of grouping developer users and controlling the access settings for these users. There is a new group called Portal Access Group that can be created for each organization. Users with access to Portal, typically developer users can now be added to the Portal Access Group. Plans and IO Docs can be added to the Portal Access Group. Users in a given Portal Access Group will get access to the Plans and IO Docs in that group when they log into the Portal.
Please contact customer support if you need the feature to be turned on for your area or want to learn more. Below are a few screen shots that go into a bit more detail on how the feature is designed and how it can be used. You can also view a recorded demo here.
Organization Control Center Users
Adding an API to an Organization
If you are a Mashery API user - if not, sign-up here! - then you might not be aware of the fact that we're passing back, in the response header, information about your usage of the API, which can help you add in more resilency to your custom API programs, e.g. if you are about to hit a QPS limit, then perhaps you want to add in a slight delay to a next call. This information can be very useful for developers building custom applications using the Mashery API.
The headers returned are:
- X-Packagekey-Qps-Allotted: The maximum QPS (queries per second) capacity set on your API key. This is the maximum number of calls that can be made in any given second.
- X-Packagekey-Qps-Current: The current count of calls being applied against the above limit; in this case, it is a representation of how many calls your key is making at that particular second in time.
- X-Packagekey-Quota-Allotted: The maximum number of calls that can be made on daily basis.
- X-Packagekey-Quota-Current: The current count of calls made in the current limit period, i.e. the current day.
- X-Plan-Quota-Reset: The time when the quota count will reset to 0.
Example response headers are below:
X-Packagekey-Qps-Allotted: 25 X-Packagekey-Qps-Current: 1 X-Packagekey-Quota-Allotted: 2000000 X-Packagekey-Quota-Current: 105094 X-Plan-Quota-Reset: Saturday, July 30, 2016 12:00:00 AM GMT
Upcoming User Experience and Feature Name Change: New Developer Management Screens and Roles to Portal Access Groups
At the end of August, all customers currently using the TIBCO Mashery API Control Center will be moved over to the new Developer Management User Experience. You can read more about that new experience here. At that time, there will be a change to the name of a feature, previously referred to as Roles or Custom Roles, which will be re-named Portal Access Groups. This feature gives you, the customer, the ability to define arbitrary role names that can be applied against content, APIs and API Plans in order to ensure that people with said roles only have access to these objects in the developer portal. You can learn more about that feature by exploring the product documentation here. We're re-naming to Portal Access Groups in order to reflect exactly what they are: a grouping of developers for the purpose of exposing different assets - content, APIs and API Plans - to them while visiting the portal.
Coincident with this change will be a new and improved user experience for managing Portal Access Groups. You can see this in action in this short demo video here. Some screenshots are displayed below.
NOTE: if you are currently using the Event Trigger Feature (blogged about here), you should be aware that there has been a slight change to the payload sent across from Mashery to your respective target endpoint. "object_type" is no longer provided; you must inspect the URI path to determine the type of object being passed to your code. If you have any questions, please contact support.
We are pleased to announce the release of a new feature within the Mashery Reporting API that will provide access to Queries per Second (QPS) details for Area, Developer key, and Endpoint objects in 30 minute summaries. This new functionality should be particularly helpful to customers seeking to manage capacity, visualize traffic spikes for any of the three objects, or generally understand traffic patterns in a new and interesting way.
In addition to pure max QPS information per 30 minute slice, the response will contain information covering data transferred and connections, which represents call concurrency.
We are excited to announce the general availability of the TIBCO Mashery V3 API. The V3 API provides a REST interface for managing the various assets in our system. The API can be used to manage User specific data, such as Members, Applications, Roles and Keys, and API related data, such as APIs, Endpoints,Methods, Packages and Plans, as well as access reporting performance data. You can use these API calls to automate the creation and management of these assets or to integrate with third party applications or create custom scripts and applications. The APIs are OAUTH2 protected and you can generate tokens by providing key and secret. Currently we have over 120 customers using these APIs, with use cases ranging from reporting data export to exporting developer data to drive email campaigns to managing the lifecycle of their APIs.
One of the challenges associated with APIs is having more and more folks be able to use them, without the often requisite sophisticated programming knowledge and experience. Interactive documentation tools, like IO Docs and Swagger UI, have been great ways for helping developers learn about APIs. But what about having people - non programmers - use APIs to accomplish day to day tasks? Imagine that! How to best get them productive all the while not having to spin up big application development projects?
TIBCO Simplr™ is a great way to get API-driven useful capabilities into the hands of business managers. TIBCO Simplr links your cloud apps and automates tasks so you can get your job done faster and more accurately. Whether you’re planning a sales trip, reporting on marketing campaigns, surveying employees, or just trying to improve your productivity, Simplr can help you and everyone in your organization.
How does this all fit into TIBCO Mashery? Well, we're pleased to announce the availabilty of the TIBCO Mashery Connector for TIBCO Simplr. TIBCO Mashery customers can now leverage a very simple tool to do things like pull developer data out of Mashery, previously only accomplished using the Mashery API. Now you can do things like pull out developer data and put into a Marketo app or a Google spreadsheet or drive a SurveyMonkey product feedback process. All without programming!
NOTE: The use of the TIBCO Mashery Connector for TIBCO Simplr requires a Mashery V3 API Key. Please visit here to get one.
TIBCO Simplr is free right now in Beta. Sign up to access Mashery connector templates, or build your own!
Flow Overview Page
Setting Up A Flow
[ Page 1 of 10 | Next ]