social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

490
active users

#apis

3 posts3 participants0 posts today

Hey, folks! I’m looking for a Staff Software Engineer to join my team (API Core) at #Mailchimp.

Some of the things we work on: #PHP, #REST, #OpenAPI, #OAuth2, #APIGovernance, and more.

We are stewards of our public #APIs, and we collaborate with other capabilities teams to ensure APIs are developed according to our standards and processes. You would work directly with me on a daily basis.

This position is in Atlanta or New York.

jobs.intuit.com/job/atlanta/st

Software Engineering Careers at IntuitStaff Software Engineer (API Core Team)Learn more about applying for Staff Software Engineer (API Core Team) at Intuit

Unmanaged #APIs create #security blindspots. 🕶️ 😧 And, as orgs build out their application ecosystems, the number of APIs integrated into IT environments expands — which can easily overwhelm security teams. ↕️ 👀 😵

Enter... API discovery.💥 Let's take a look at:

❓ What API discover is
⚠️ The risks that undocumented and unmanaged APIs pose
❗ Why #API discovery is important
🤖 Using automation for API discovery
👁️ What to look for in an API discovery tool

graylog.org/post/why-api-disco #cybersecurity #SIEM

"Getting to this point isn’t unusual. Clients clearly think they’re making the call correctly, or else they would fix the endpoint themselves. Some misspellings are difficult to catch. The enum USER_RETREIVE may not be noticed from USER_RETRIEVE, especially if picking it from a list. Misspellings happen and they’re not always caught before making it to the contract. As an aside, that’s why it’s important writers routinely check development’s changes. This applies, too, to our testing calls in Postman, where manually entering endpoints and values are more pervasive.

The reason this isn’t caught is simple: We’re not expecting it.

For our testing, the call is made and we get results. We may even spot check some of them. But generally, results aren’t examined that closely. For instance, how often do you so carefully examine a returned list of 50 or 100 items? You check may check that the objects are complete but not that the list conforms to the search criteria.

The reason this happens is because of an intentional behavior on the server. This behavior is called Lenient Handling or Strict Handling."

robertdelwood.medium.com/under

Medium · Understanding Query Parameter Handling in REST CallsBy Robert Delwood
#APIs#RESTAPIs#Rest
Continued thread

- Estabilización de Event Replay en SSR:

Se robustece el mecanismo de replay de eventos en Server-Side Rendering, buscando un comportamiento más predecible y consistente. 🔄 #SSR

- Nuevas APIs: `resource` y `rxResource`:

Se incorporan nuevas APIs para la gestión de recursos y operaciones HTTP reactivas, integrándose con el modelo de Signals. 🧰 #Signals #APIs

Adios Rxjs??